# InBox TicketCron

Version 7.0.2

Date of Creation 04/30/2019

# Resources

This module provides the option to schedule the creation of tickets.

# Prerequisites

# Framework

The following versions of the Znuny framework are supported:

• [7.0.x]

# Modules

The following modules are required:

- InBox Core 7.0.1 or higher

# Operational system

The following operating systems are required:

• [None]

# Third Party Software

The following third party software is required:

• [None]

# Installation

bin/otrs.Console.pl Admin::Package::Install /path/to/InBox\ TicketCron-7.0.2.opm

# Configuration

# Configuring UTC Time Zone

Access by the way: InBox > TicketCron > Core

# Configuring UTC OTRSTimeZone

In system configuration, search for OTRSTimeZone:

Note: The two settings above must be in the same time zone.

# Configuring Dynamic Fields

Access the link: http://localhost/otrs/index.pl?Action=AdminSystemConfigurationGroup;RootNavigation=InBox::TicketCron::DynamicField

Or access by the way: InBox > TicketCron > DynamicField

NOTE: Only possible for native fields of type: text, drop-down, date and date / time. You can configure dynamic fields by their name. Set 1-enabled or 0-disabled.

# Invalidate Services

To invalidate services, go to "Administration > System Configuration" and search for: "TicketCron::ServicesBlackList", enter the IDs of the unwanted services and save.

# Usage

# Accessing Ticket Cron

You can set up a ticket schedule using the TicketCron option, in the 'Users, Groups & Functions' block, in the OTRS administration.

Access the link: http://localhost/otrs/index.pl?Action=Admin

# Knowing the Ticket Cron Panel

Through this panel you can view the already created scheduled tickets, add a new creation task, execute a task or delete an existing one.

# Performing a task

In the task list, click (‘Create ticket’), the system will process the creation of the new ticket. Wait for the success message to display.

# Last run info

Note that when displaying (‘Last run‘) the system informs the acronyms (M) or (AT). These acronyms represent that the last execution of the task in question was performed manually (M), or by scheduling (AT).

# Creating a new task

Clicking on (‘Add Task‘) will make the following settings available:

# Task Configuration

Task name and validity

# Runtime Configuration

The example in the image will run every day 10 and 13 at 1:05pm, 1:10pm, 1:25pm every month of November.

Configure the periodicity of the task execution, based on: minutes, hours, days, days of the week and months.

Ticket attributes are the common ticket opening settings. Remembering that the field 'Body' has a limit of 250 characters.

# DynamicFieldFileSystem

To add file attachment in cron ticket must have the module DynamicFieldFileSystem installed on the machine.

the dynamic field name should be added in the configuration: "TicketCron::DynamicFieldFileSystem"

After created only adds it on the screen of the cron ticket . Info: The cron ticket name cannot have space if you are going to use the "_".